Method and apparatus for processing NAS signaling request in wireless communication system

ABSTRACT

The present invention relates to a wireless communication system, and more particularly, to a method and an apparatus for processing a NAS signaling request. A method for performing a non-access stratum (NAS) signaling process by means of a terminal in a wireless communication system according to one embodiment of the present invention comprises: a step of receiving a first message that includes information indicating a network failure from a network node of a first network; a step of starting a timer relating to a network selection; and a step of selecting a second network from among network candidates excluding the first network during the operation of the timer relating to a network selection.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/995,108, filed on Jan. 13, 2016, now U.S. Pat. No. 9,713,055, whichis a continuation of U.S. patent application Ser. No. 14,559,702, filedon Dec. 3, 2014, now U.S. Pat. No. 9,271,172, which is a continuation ofU.S. patent application Ser. No. 14/365,054, filed on Jun. 12, 2014, nowU.S. Pat. No. 8,934,334, which is the National Stage filing under 35U.S.C. 371 of International Application No. PCT/KR2013/002192, filed onMar. 18, 2013, which claims the benefit of U.S. Provisional ApplicationNos. 61/612,204, filed on Mar. 16, 2012, 61/619,917, filed on Apr. 3,2012, and 61/645,633, filed on May 11, 2012, the contents of which areall hereby incorporated by reference herein in their entirety.

TECHNICAL FIELD

The following description relates to a wireless communication systemand, more particularly, to a method and apparatus for processing anon-access stratum (NAS) signaling request.

BACKGROUND ART

NAS corresponds to the highest stratum of a control plane between userequipment (UE) and a network node (e.g. mobility management entity(MME)) in a wireless communication system. NAS protocols includeprotocols for mobility management (NN) and session management (SM)between the UE and MME. For example, evolved packet system (EPS) MMM(EMM) protocol can provide procedures for controlling UE mobility andsecurity of NAS protocols. EPS SM (ESM) protocol can include a procedureof processing EPS bearer context and can be used for bearer controlprovided by an access stratum (AS) and user plane bearer control.

DISCLOSURE Technical Problem

An object of the present invention devised to solve the problem lies ina method for efficiently processing a NAS signaling request when the NASsignaling request fails or is rejected due to lower layer failure ornetwork failure during a NAS signaling procedure.

The technical problems solved by the present invention are not limitedto the above technical problems and those skilled in the art mayunderstand other technical problems from the following description.

Technical Solution

The object of the present invention can be achieved by providing amethod for performing a non-access stratum (NAS) signaling procedure bya UE in a wireless communication system, the method including: receivinga first message including information indicating network failure from anetwork node of a first network; starting a network selection relatedtimer; and selecting a second network from among network candidatesother than the first network while the network selection related timeris running.

In another aspect of the present invention, provided herein is a UEperforming a NAS signaling procedure in a wireless communication system,including: a transmission and reception module; and a processor, whereinthe processor is configured to receive a first message includinginformation indicating network failure from a network node of a firstnetwork using the transmission and reception module, to start a networkselection related timer and to select a second network from amongnetwork candidates other than the first network while the networkselection related timer is running.

The following can be commonly applied to the above-described aspects ofthe present invention.

The first network is may be a public land mobile network (PLMN)providing the information indicating network failure.

The selecting of the second network may include selecting at least oneof a radio access technology (RAT) or a PLMN from candidates other thana combination of a RAT and a PLMN providing the information indicatingnetwork failure.

The method may further include transmitting, to the network node of thefirst network, a second message for request of the NAS signalingprocedure.

The first message may be a rejection message indicating that the NASsignaling procedure requested through the second message is not grantedby a network.

The second message may correspond to one of an attach request message, atracking area update (TAU) request message, a routing area update (RAU)request message, or a service request message.

The first message may correspond to one of an attach reject message, aTAU reject message, an RAU reject message, or a service reject message.

The method may further include setting an attempt counter to the upperbound thereof when the first message corresponds to one of the attachreject message, the TAU reject message, or the RAU reject message.

A value of the upper bound may be 5.

The update status of the UE may be set to NOT UPDATED.

At least one of a globally unique temporary identifier (GUTI), lastvisited registered tracking area identity (TAI), key set identifier(KSI) information, or a list of equivalent PLMNs may be deleted.

The UE may be set to EMM-DEREGISTERED.PLMN-SEARCH state

When the UE supports A/Gb mode or Iu mode, at least one of packettemporary mobile subscriber identity (P-TMSI), P-TMSI signature, routingarea identity (RAI), or a general packet radio service (GPRS) cipheringkey sequence number may be deleted.

The network node may be a mobile management entity (MME).

The above description and the following detailed description of thepresent invention are exemplary and are for additional explanation ofthe invention disclosed in the claims.

Advantageous Effects

According to the present invention, it is possible to provide a methodfor efficiently processing a NAS signaling request when the NASsignaling request fails or is rejected due to lower layer failure ornetwork failure during a NAS signaling procedure.

The effects of the present invention are not limited to theabove-described effects and other effects which are not described hereinwill become apparent to those skilled in the art from the followingdescription.

DESCRIPTION OF DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the invention, illustrate embodiments of the inventionand together with the description serve to explain the principle of theinvention. In the drawings:

FIG. 1 illustrates a configuration of an EPS including an evolved packetcore (EPC);

FIG. 2 illustrates a control plane for interface among a UE, an eNB andan MME;

FIGS. 3(a) and 3(b) illustrate an attach procedure;

FIGS. 4(a) and 4(b) illustrate a TAU procedure;

FIGS. 5(a) and 5(b) illustrate a service request procedure;

FIG. 6 is a flowchart illustrating a method for performing a NASsignaling procedure according to an embodiment of the present invention;and

FIG. 7 illustrates a configuration of a UE according to an embodiment ofthe present invention.

BEST MODE

The embodiments of the present invention described hereinbelow arecombinations of elements and features of the present invention. Theelements or features may be considered selective unless otherwisementioned. Each element or feature may be practiced without beingcombined with other elements or features. Further, an embodiment of thepresent invention may be constructed by combining parts of the elementsand/or features. Operation orders described in embodiments of thepresent invention may be rearranged. Some constructions of any oneembodiment may be included in another embodiment and may be replacedwith corresponding constructions of another embodiment.

Specific terms used for the embodiments of the present invention areprovided to aid in understanding of the present invention. Thesespecific terms may be replaced with other terms within the scope andspirit of the present invention.

In some cases, to prevent the concept of the present invention frombeing ambiguous, structures and apparatuses of the known art will beomitted, or will be shown in the form of a block diagram based on mainfunctions of each structure and apparatus. Also, wherever possible, thesame reference numbers will be used throughout the drawings and thespecification to refer to the same or like parts.

The embodiments of the present invention can be supported by standarddocuments disclosed for at least one of wireless access systems,Institute of Electrical and Electronics Engineers (IEEE) 802, 3^(rd)Generation Partnership Project (3GPP), 3GPP Long Term Evolution (3GPPLTE), LTE-Advanced (LTE-A), and 3GPP2. Steps or parts that are notdescribed to clarify the technical features of the present invention canbe supported by these documents. Further, all terms as set forth hereincan be explained by the standard documents.

The following technology can be used in various wireless communicationsystems. While the following description is made based on 3GPP LTE and3GPP LTT-A, the technical scope of the present invention is not limitedthereto.

Terms used in the specification are defined as follows.

-   -   UMTS (Universal Mobile Telecommunication System): GSM (Global        System for Mobile Communication) based third generation mobile        communication technology developed by 3GPP    -   EPS (Evolved Packet System): a network system composed of an EPC        (Evolved Packet Core) corresponding to an IP based packet        switched core network and an access network such as LTE, UTRAN,        etc., which evolved from UMTS.    -   NodeB: an eNB of GERAN/UTRAN which is installed outdoors and has        coverage of a macro cell.    -   eNodeB: an LTE eNB which is installed outdoors and has coverage        of a macro cell.    -   HNB (Home NodeB): CPE (Customer Premises Equipment) providing        UTRAN (UMTS Terrestrial Radio Access Network) coverage. Refer to        standard document TS 25.467 for details.    -   HeNB (Home eNodeB): CPE providing E-UTRAN (Evolved-UTRAN)        coverage. Refer to standard document TS 36.300 for details.    -   UE (User Equipment): referred to as a terminal, ME (Mobile        Equipment), MS (Mobile Station), etc. The UE may be a portable        device such as a notebook computer, cellular phone, PDA        (Personal Digital Assistant), smartphone, multimedia device,        etc. or a fixed device such as a PC (Personal Computer), vehicle        mounted device, etc. The UE can perform communication through        3GPP spectrum such as LTE and/or non-3GPP spectrum such as WiFi,        public safety spectrum, etc.    -   RAN (Radio Access Network): a unit including NodeB, eNodeB and        RNC (Radio Network Controller) for controlling NodeB and eNodeB        in a 3GPP network. The RAN is present between a UE and a core        network and provides connection to the core network.    -   MME (Mobility Management Entity): an EPS network node which        performs mobility management (MM) and session management (SM).    -   HLR (Home Location Register)/HSS (Home Subscriber Server): a        database including subscriber information of a 3GPP network. HSS        can perform configuration storage, identity management and user        state storage, etc.    -   PDN-GW (Packet Data Network-Gateway)/PGW: an EPS network node        which performs UE IP address assignment, packet screening and        filtering, charging data collection, etc.    -   SGW (Serving Gateway): an EPS network node which performs        mobility anchoring, packet routing, idle mode packet buffering,        triggering an MME to page a UE, etc.    -   PCRF (Policy and Charging Rule Function): an EPS network node        which performs policy decision for dynamically applying QoS        (Quality of Service) and charging policy discriminated per        service flow.    -   OMA DM (Open Mobile Alliance Device Management): a protocol        which is designed to manage mobile devices such as cellular        phones, PDA, portable computers, etc. and performs device        configuration, firmware upgrade, error reporting, etc.    -   OAM (Operation Administration and Maintenance): a network        management function set providing network defect indication,        performance information, data and diagnosis function.    -   NAS (Non-Access Stratum): A higher stratum of a control plane        between a UE and an MME. The NAS is a functional layer for        signaling between a UE and a core network and exchanging a        traffic message between the UE and core network in LTE/UMTS        protocol stack and supports UE mobility and a session management        procedure for establishing and maintaining IP connection between        a UE and PDN GW.    -   NAS configuration MO (Management Object): a management object        used to configure NAS functionality related parameters for a UE.    -   PDN (Packet Data Network): a network in which a server        supporting a specific service (e.g. MMS (Multimedia Messaging        Service) server, WAP (Wireless Application Protocol) server,        etc.) is located.    -   PDN connection: a logical connection between a UE and a PDN,        represented by one IP address (one IPv4 address and/or one IPv6        prefix).    -   APN (Access Point Name): a string for indicating or identifying        a PDN. A requested service or network (PDN) is accessed through        a corresponding PGW. A name (string) is pre-defined in the        network to detect the PGW. For example, APN can be represented        as internet.mnc012.mcc345.gprs.    -   AS (Access-Stratum): a stratum including a protocol stack        between a UE and a radio network or between the UE and an access        network and transmitting data and network control signals.    -   Lower layer failure: failure that cannot be corrected at AS        level and is reported by the AS to the NAS. When the AS signals        lower layer failure to the NAS, NAS signaling connection cannot        be used.    -   PLMN (Public Land Mobile Network): a network configured to        provide a mobile communication service to individuals. The PLMN        can be configured per operator.

EPC (Evolved Packet Core)

FIG. 1 illustrates a configuration of an EPC.

The EPC is a core element of system architecture evolution (SAE) forimproving performance of 3GPP technology. SAE corresponds to a researchproject for determining a network structure supporting mobility betweenvarious types of networks. For example, SAE aims to provide an optimizedpacket-based system for supporting various radio access technologies andproviding enhanced data transmission capability.

Specifically, the EPC is a core network of an IP mobile communicationsystem for 3GPP LTE and can support real-time and non-real-timepacket-based services. In conventional mobile communication systems(i.e. second-generation or third-generation mobile communicationsystems), functions of a core network are implemented through acircuit-switched (CS) sub-domain for audio and a packet-switched (PS)sub-domain for data. However, in 3GPP LTE evolved from third-generationmobile communication systems, CS and PS sub-domains are unified into oneIP domain. That is, connection of terminals having IP capability can beestablished through a base station (e.g. eNodeB (evolved Node B)), EPCand application domain (e.g. IMS) in 3GPP LTE. That is, the EPC is anessential element for end-to-end IP services.

The EPC may include various components. FIG. 1 illustrates some of thecomponents, that is, a SGW (Serving Gateway), PDN GW (Packet DataNetwork Gateway), MME (Mobility Management Entity), SGSN (Serving GPRS(General Packet Radio Service) Supporting Node) and ePDG (enhancedPacket Data Gateway).

The SGW operates as a boundary point between a radio access network(RAN) and a core network and maintains a data path between an eNodeB andthe PDN GW. When a terminal moves over an area served by an eNodeB, theSGW functions as a mobile anchor point. That is, packets can be routedthrough the SGW for mobility in E-UTRAN (Evolved-UMTS (Universal MobileTelecommunications System) Terrestrial Radio Access Network definedafter 3GPP release-8). In addition, the SGW may function as an anchorpoint for mobility with respect to another 3GPP networks (RAN, forexample, UTRAN or GERAN (GSM (Global System for MobileCommunication)/EDGE (Enhanced Data rates for Global Evolution) RadioAccess Network defined after 3GPP release-8).

The PDN GW corresponds to a termination point of a data interface towarda packet data network. The PDN GW can support policy enforcementfeatures, packet filtering, charging support, etc. In addition, the PDNGW may function as an anchor point for mobility management with respectto unreliable networks such as 3GPP and non-3GPP networks (e.g. I-WLAN(Interworking Wireless Local Area Network)) and reliable networks suchas CDMA (Code Division Multiple Access) and WiMax networks.

While FIG. 1 shows that the SGW and PDN GW are configured as separategateways, the two gateways may be implemented according to a singlegateway configuration option.

The MME is an element which executes signaling and control functions forsupporting terminal access for network connection, network resourceallocation, tracking, paging, roaming and handover. The MME controlscontrol plane functions related to subscriber and session management.The MME manages a large number of eNodeBs and performs signaling forselecting a conventional gateway for handover to other 2G/3G networks.In addition, the MME performs security procedures, terminal-to-networksession handling, idle terminal location management, etc.

The SGSN handles packet data such as user mobility management andauthentication with respect to other 3GPP networks (e.g. GPRS network).

The ePDG functions as a security node for unreliable non-3GPP networks(e.g. I-WLAN, Wi-Fi hotspot, etc.).

As described above with reference to FIG. 1, a terminal having IPcapability can access an IP service network (e.g. IMS) provided by anoperator via various elements in the EPC based on non-3GPP access aswell as 3GPP access.

In addition, FIG. 1 shows various reference points (e.g. S1-U, S1-MME,etc.). In 3GPP, a conceptual link connecting two functions of differentfunctional entities of an E-UTRAN and an EPC is defined as a referencepoint. Table 1 arranges the reference points illustrated in FIG. 1.Various reference points may be present according to network structurein addition to the reference points shown in Table 1.

TABLE 1 Reference point Description S1-MME Reference point for a controlplane protocol between an E-UTRAN and an MME S1-U Reference pointbetween an E-UTRAN and an SGW with respect to path switching betweeneNodeBs during handover and user plane tunneling per bearer S3 Referencepoint between an MME and an SGSN to provide user and bearer informationexchange for mobility between 3GPP access networks in idle and/or activestate (This reference point can be used in PLMN or between PLMNs (in thecase of handover between PLMNs, for example).) S4 Reference pointbetween an SGW and an SGSN to provide control related to 3GPP anchorfunctions of a GPRS core and the SGW and support mobility between theGPRS core and SGW. When a direct tunnel is not formed, this referencepoint provides user plane tunneling. S5 Reference point providing userplane tunneling between an SGW and a PDN GW and tunnel management. Thisreference point is used for SGW rearrangement when the SGW needs to beconnected to the PDN GW which is not located with the SGW due to UEmobility and for required PDN connectivity. S11 Reference point betweenan MME and an SGW SGi Reference point between a PDN GW and a PDN. ThePDN may be a common or private PDN outside an operator or a PDN insidethe operator for providing IMS service. This reference point correspondsto Gi of 3GPP access.

S2 a and S2 b from among the reference points shown in FIG. 1 correspondto non-3GPP interfaces. S2 a is a reference point which providesreliable non-3GPP access, related control and mobility support betweenPDN GWs to a user plane. S2 b is a reference point which providesrelated control and mobility support between the ePDG and the PDN GW tothe user plane.

FIG. 2 illustrates a control plane with respect to interfaces among aUE, an eNB and an MME.

The MME can perform access control for the UE that attempts access andan interface and protocol stack used therefor are as shown in FIG. 2.From among the interfaces shown in FIG. 2, a control plane interfacebetween the UE and the eNB is defined as LTE-Uu and a control planeinterface between the eNB and the MME is defined as S1-MME.

A NAS protocol forms a highest stratum in the control plane between theUE and the MME. The NAS protocol can support UE mobility management andsession management to establish and maintain IP connectivity between theUE and PDN GW. In addition, the NAS protocol can define a rule formapping of parameters with respect to mobility between systems andprovide NAS security through NAS signaling message encryption andintegrity protection.

An EMM (EPS Mobility Management) specific procedure may include anattach procedure, a detach procedure and a TAU (Tracking Area Update)procedure. An EMM connection management procedure may include a servicerequest procedure.

FIGS. 3(a) and 3(b) illustrate the attach procedure.

The attach procedure is used to attach a UE to an EPC for a packetservice of the EPC. The attach procedure can be used for a case in whicha UE operating in a PS mode attaches to an EPS service, a UE operatingin a CS/PS mode attaches to both EPS and non-EPS services or a UEattaches for emergency bearer services.

Referring to FIG. 3(a), an EMM-deregistered UE may initiate an attachprocedure by transmitting an attach request message to an MME. The UEmay include EPS mobility identification information in the attachrequest message. When the attach request is granted in the correspondingnetwork, the MME may transmit an attach accept message to the UE. Inaddition, the MME may provide information for instructing the UE toperform EPS bearer context activation to the UE. Upon reception of theattach accept message from the MME and EPS bearer context activation,the UE may transmit an attach complete message to the MME.

Referring to FIG. 3(b), when the attach request is not granted in thenetwork although the UE has transmitted the attach request message tothe MME, the MME may transmit an attach reject message to the UE. Theattach reject message may include a value indicating the cause of attachrejection.

FIGS. 4(a) and 4(b) illustrate the TAU procedure.

TAU is always initiated by a UE and can be used to update registrationof tracking area of the UE or to periodically notify the network ofavailability of the UE.

Referring to FIG. 4(a), an EMM-registered UE may initiate the TAUprocedure by transmitting a TAU request message to the MME. For example,the TAU procedure can be initiated upon detecting that the UE hasentered a tracking area which is not included in a tracking area list ofthe UE. When the TAU request is granted in the network, the MME maytransmit a TAU accept message to the UE. If the MME allocates a new GUTI(Globally Unique Temporary Identifier) to the UE, then the GUTI can beincluded in the TAU accept message. Upon reception of the TAU acceptmessage including the GUTI, the UE may transmit a TAU complete messageto the MME as acknowledgement of the received GUTI.

Referring to FIG. 4(b), when the TAU request is not granted in thenetwork although the UE has transmitted the TAU request message to theMME, the MME may transmit a TAU reject message to the UE. The TAU rejectmessage may include a value indicating the cause of TAU rejection.

FIGS. 5(a) and 5(b) illustrate the service request procedure.

The service request procedure can be used to switch a UE in an EMM-idlemode to an EMM-connected mode and to establish radio bearer and S1bearer such that uplink user data or signaling can be transmitted. Inaddition, the service request procedure may be used to operate mobileoriginated (MO)/mobile terminated (MT) CS fallback (CSFB). For example,the service request procedure can be used for cases in which a networkhas downlink signaling to be transmitted, a UE has uplink signaling tobe transmitted and the UE or the network has user data to be transmittedwhile the UE is in the EMM-idle mode.

Referring to FIG. 5(a), the UE may initiate the service requestprocedure by transmitting a service request message or an extendedservice request message to the MME. Upon reception of the (extended)service request message, the MME may perform authentication and securitymode control. Upon reception of indication that user plane radio bearerhas been set and indication of system change from a lower layer (e.g.AS), the UE may process the indications as an indication that theservice request procedure has been successfully completed. Accordingly,the UE can enter an EMM-registered state.

Referring to FIG. 5(b), when the (extended) service request message isnot granted in the network although the UE has transmitted the messageto the MME, the MME may transmit a TAU service reject message to the UE.The service reject message may include a value indicating the cause forrejection.

In the aforementioned NAS protocol (e.g. attach procedure, TAU procedureand/or service request procedure), a NAS signaling request may fail orbe rejected due to lower layer (e.g. AS) failure or network failure,which will be described in detail later.

In the attach procedure, the following abnormal cases in the UE can beidentified.

a) When access is barred because of access class barring or NASsignaling connection establishment rejection by the network

If access is barred for “signaling”, then the attach procedure is notstarted. The UE stays in the current serving cell and applies the normalcell reselection process. The attach procedure is started when accessfor “signaling” is granted on the current cell or when the UE moves to acell where access for “signaling” is granted.

b) When NAS signaling connection is released or lower layer failure isgenerated before the attach accept message or the attach reject messageis received

The attach procedure is aborted, and the UE may proceed as describedbelow.

c) In case of T3410 timeout

T3410 is started when the attach request message is transmitted and canbe set to 15 seconds, for example. The UE aborts the attach procedureand proceeds as described below. The NAS signaling connection isreleased.

-   -   d) When the attach reject message includes other EMM cause        values than #3, #6, #8, #11, #35, #12, #13, #14, #15, #22 and        #25 and the UE considers EMM cause value #22 as an abnormal case

Upon reception of EMM cause value #19 “ESM failure”, if the UE is notconfigured for NAS signaling low priority, the UE may set an attachattempt counter to 5. Upon reception of EMM cause values #95, #96, #97,#99 and #111, the UE needs to set the attach attempt counter to 5. TheUE may proceed as described below.

Here, EMM cause value #3 indicates an illegal UE, #6 indicates illegalmobile equipment (ME), #7 indicates that EPS service is not granted, #8indicates that EPS service and non-EPS service are not granted, #11indicates a non-granted PLMN, #35 indicates that a requested serviceoption is not authorized in the corresponding PLMN, #12 indicates anon-granted tracking area, #13 indicates that roaming is not granted inthe corresponding tracking area, #14 indicates that EPS service is notgranted in the corresponding PLMN, #15 indicates that an appropriatecell is not present in a tracking area, #22 indicates congestion, and#25 indicates that a corresponding CSG (closed subscriber group) is notauthorized. These values are exemplary EMM cause values when an attachrequest is not granted by the network.

The case in which the UE considers EMM cause value #22 as an abnormalcase corresponds to cases other than a case in which the attach rejectmessage includes a predetermined timer (e.g. T3346 corresponding to anMM backoff timer set when NAS level MM congestion control is activated,MM signaling is normally barred during operation of T3346) and the timeris set to a non-zero value and is not deactivated.

e) In the case of change of cell into a new tracking area

If a cell change into a new tracking area occurs before the attachprocedure is completed, the attach procedure is aborted and immediatelyre-initiated. If a tracking area border is crossed when the attachaccept message has been received but before an attach complete messageis sent, then the attach procedure is re-initiated. When a GUTI has beenallocated during the attach procedure, the GUTI is used in the attachprocedure.

f) When mobile originated (MO) detach is required

The attach procedure is aborted, and a UE initiated detach procedure isperformed.

g) In the case of detach procedure collision

When the UE in an EMM-registered-initiated sate receives a detachrequest message from the network and the detach type indicates“re-attach not required”, the detach procedure progresses and the attachprocedure is aborted. Otherwise the attach procedure progresses and thedetach request message is ignored.

h) When a lower layer indicates attach request message transmissionfailure

The UE restarts the attach procedure.

i) When a lower layer indicates attach complete message transmissionfailure

If the current TAI is not included in a TAI list, then the UE restartsthe attach procedure. If the current TAI is still in the TAI list, it isdetermined whether the ongoing procedure is re-run according to UEimplementation. An EMM sublayer may notify an ESM sublayer that the ESMmessage in the ESM message container information element of the attachcomplete has failed to be transmitted.

j) When an activate default bearer context request message combined withthe attach accept is not accepted by the UE due to failure in a UE ESMsublayer

The UE initiates the detach procedure by sending a detach requestmessage to the network. Further UE behavior is implementation specific.

k) When a lower layer indicates that an S101 mode to S1 mode handoverhas been cancelled (i.e. S101 mode only)

The UE aborts the attach procedure and entersEMM-DEREGISTERED.NO-CELL-AVAILABLE state.

l) When a lower layer indicates “extended wait time”

The UE stops the MM backoff timer (e.g. T3346) if it is running The MMbackoff timer is started with the value provided by a lower layer in the“extended wait time” and the state is changed toEMM-DEREGISTERED.ATTEMPTING-TO-ATTACH state. The UE aborts the attachprocedure, resets an attach attempt counter, stays in the currentserving cell and applies the normal cell reselection process. The UE mayproceed as described below.

m) When the MM backoff timer T3346 is running

The UE does not start the attach procedure unless the UE needs to attachfor emergency bearer services. The UE stays in the current serving celland applies the normal cell reselection process.

Here, it is considered an abnormal case if the UE needs to initiate anattach procedure while timer T3346 is running independently of whethertimer T3346 has been started due to an abnormal case or an unsuccessfulcase.

For the cases b), c), and d), the UE proceeds as follows. Timer T3410,which is started when the attach request message is transmitted, isstopped if still running The attach attempt counter is incremented,unless already set to 5.

If the attach attempt counter is less than 5, the UE operates asfollows. For the cases l) and m), the attach procedure is started, ifstill necessary, when timer T3346 expires or is stopped. For all othercases, timer T3411 (i.e. timer which is started in the case of attachfailure or TAU failure due to lower layer failure or attach rejection orTAU rejection due to other EMM cause values than abnormal cases andstopped when an attach request or a TAU request is transmitted) isstarted and the state is changed toEMM-DEREGISTERED.ATTEMPTING-TO-ATTACH state. When timer T3411 expires,the attach procedure is restarted if still required by the ESM sublayer.

When the attach attempt counter is equal to 5, the UE operates asfollows. The UE deletes a GUTI, TAI list, last visited registered TAI,list of equivalent PLMNs and KSI (Key Set Identifier) if present. Inaddition, the UE sets the update status to NOT UPDATED (e.g. EU2) andstarts timer T3402 (i.e. timer which is started when the attempt counteris 5 in the case of attach failure or TAU failure and stopped when anattach request or a TAU request is transmitted). The state may bechanged to EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH state or optionally toEMM-DEREGISTERED.PLMN-SEARCH state in order to perform PLMN selection.

When A/Gb mode or Iu mode (i.e. a mode using interfaces for accessing acore network defined in GERAN system prior to 3GPP release-8) issupported by the UE, the UE additionally deletes RAI (Routing AreaIdentity), P-TMS (Packet Temporary Mobile Subscriber Identity), P-TSMIsignature, equivalent PLMN lest and GPRS ciphering key sequence numberif present when a normal attach procedure fails and the attach attemptcounter is equal to 5. In addition, the UE sets the update status to NOTUPDATED (e.g. GU2) and starts timer T3302 (i.e. timer which is startedwhen the attempt counter is greater than 5 in the case of GPRS attachfailure or RAU failure and stopped when a GPRS attach request or an RAUrequest is transmitteD). The state may be changed toGMM-DEREGISTERED.ATTEMPTING-TO-ATTACH state or optionally toGMM-DEREGISTERED.PLMN-SEARCH state in order to perform PLMN selection.

In the TAU procedure, the following abnormal cases can be identified inthe UE.

a) When access is barred because of access class barring or NASsignaling connection establishment rejection by the network

When access is barred for “signaling”, the TAU procedure is not started.The UE may stay in the current serving cell and apply the normal cellreselection process. The TAU procedure can be started when access for“signaling” is granted on the current cell or when the UE moves to acell where access for “signaling” is granted and if still necessary.

b) When NAS signaling connection is released or lower layer failure isgenerated before the TAU accept message or the TAU reject message isreceived

The TAU procedure is aborted, and the UE may proceed as described below.

c) In the case of T3430 timeout

T3430 is started when the TAU request message is transmitted and can beset to 15 seconds, for example. The UE aborts the TAU procedure andproceeds as described below. The NAS signaling connection is released.

d) When the TAU reject message includes other EMM cause values than #3,#6, #7, #9, #10, #11, #35, #12, #13, #14, #15, #22, #25 and #40 and theUE considers EMM cause value #22 as an abnormal case

Upon reception of EMM cause values (e.g. #95, #96, #97 and #99)indicating protocol error, the UE needs to set the TAU attempt counterto 5. The UE may proceed as described below.

Here, EMM cause value #3 indicates an illegal UE, #6 indicates illegalmobile equipment (ME), #9 indicates that UE identification informationis not derived from the network, #10 indicates implicit detach, #11indicates non-granted PLMN, #35 indicates that a requested serviceoption is not authorized in the corresponding PLMN, #12 indicates anon-granted tracking area, #13 indicates that roaming is not granted inthe corresponding tracking area, #14 indicates that EPS service is notgranted in the corresponding PLMN, #15 indicates that an appropriatecell is not present in a tracking area, #22 indicates congestion, #25indicates that a corresponding CSG (closed subscriber group) is notauthorized, and #40 indicates that activated EPS bearer context is notpresent. These values are exemplary EMM cause values when a TAU requestis not granted by the network.

The case in which the UE considers EMM cause value #22 as an abnormalcase corresponds to cases other than a case in which the TAU rejectmessage includes a predetermined timer (e.g. T3346 corresponding to anMM backoff timer set when NAS level MM congestion control is activated,MM signaling is normally barred during operation of T3346) and the timeris set to a non-zero value and is not deactivated.

e) In the case of cell change into a new tracking area

If a cell change into a new tracking area occurs before the TAUprocedure is completed, then the TAU procedure is aborted andimmediately re-initiated. The UE sets the EPS update status to NOTUPDATED (e.g. EU2).

f) When the TAU procedure and the detach procedure collide

If the UE receives a detach request message with detach type “re-attachnot required” with EMM cause values other than EMM cause value #2indicating “IMSI unknown in HSS” or detach type “re-attach required”before the TAU procedure has been completed, then the TAU procedure isaborted and the detach procedure progresses.

If the UE receives a detach request message with detach type “re-attachnot required” with EMM cause value #2 indicating “IMSI unknown in HSS”or detach type “IMSI detach” before the TAU procedure has beencompleted, then the detach request message is ignored and the TAUprocedure progresses.

g) When the TAU procedure and GUTI reallocation procedure collide

If the UE receives a GUTI reallocation command message before the TAUprocedure has been completed, then the message is ignored and the TAUprocedure progresses.

h) When a lower layer indicates TAU request message transmission failure

The TAU procedure is aborted and re-initiated immediately. The UE setsthe EPS update status to NOT UPDATED (e.g. EU2).

i) When a lower layer indicates TQU complete message transmissionfailure with TAI change

If the current TAI is not on the TAI list, then the TAU procedure isaborted and immediately re-initiated. The UE sets the EPS update statusto NOT UPDATED (e.g. EU2). If the current TAI is still part of the TAIlist, it is determined whether the ongoing procedure is re-run accordingto UE implementation.

j) When a lower layer indicates TAU complete message transmissionfailure without TAI change

It is determined whether the ongoing procedure is re-run according to UEimplementation.

k) When a lower layer indicates “extended wait time”, the UE stops an MMbackoff timer (e.g. T3346) if it is running. The MM backoff timer isstarted with the value provided by the lower layer in the “extended waittime”, the EPS update status is set to NOT UPDATED (e.g. EU2) andchanged to EMM-REGISTERED.ATTEMPTING-TO-UPDATE state. The UE aborts theTAU procedure, resets the TAU attempt counter, stays in the currentserving cell and applies the normal cell reselection process. The UE mayproceed as described below.

l) When MM backoff timer T3346 is running, the UE does not start the TAUprocedure unless the UE is establishing a PDN connection for emergencybearer services, has a PDN connection for emergency bearer servicesestablished or is in EMM-CONNECTED mode. The UE stays in the currentserving cell and applies the normal cell reselection process.

Here, it is considered an abnormal case if the UE needs to initiate aTAU procedure while timer T3346 is running independently of whethertimer T3346 has been started due to an abnormal case or an unsuccessfulcase.

For cases b), c), d), e), and k), the UE stops any ongoing transmissionof user data.

For cases b), c), d), k) and l), the UE proceeds as follows:

Timer T3430 is stopped if still running

For cases b), c) and d), the TAU attempt counter is incremented, unlessit was already set to 5.

If the TAU attempt counter is less than 5, the TAI of the currentserving cell is included in the TAI list, the EPS update status isUPDATED (e.g. EU1) and TIN (Temporary Identity used in Next update) doesnot indicate “P-TMSI”, then the UE operates as follows. The UE keeps theEPS update status to EU1 and enters EMM-REGISTERED.NORMAL-SERVICE state.The UE starts timer T3411 (i.e. timer which is started in the case ofattach failure or TAU failure due to lower layer failure or attachrejection or TAU rejection due to other EMM cause values than abnormalcases and stopped when an attach request or a TAU request istransmitted). If the TAU request indicates “periodic updating”, thetimer T3411 may be stopped when the UE enters EMM-CONNECTED mode. Iftimer T3411 expires, the TAU procedure is triggered again.

If the TAU attempt counter is less than 5, the TAI of the currentserving cell is not included in the TAI list or the EPS update status isdifferent from EU1 or the TIN indicates “P-TMSI”, the UE operates asfollows. For cases k) and l), the TAU procedure is started, if stillnecessary, when timer T3346 expires or is stopped. For all other cases,the UE starts timer T3411, sets the EPS update status to NOT UPDATED(e.g. EU2) and changes the state to EMM-REGISTERED.ATTEMPTING-TO-UPDATEstate. When timer T3411 expires, the TAU procedure is triggered again.If A/Gb mode or Iu mode is supported by the UE, the UE starts the timerT3311 (i.e. timer which is started in the case of RAU rejection andstopped when RA is changed or RAU process is initiated), sets GPRSupdate status to NOT UPDATED (e.g. GU2) and changes that state toGMM-REGISTERED.ATTEMPTING-TO-UPDATE state for the abnormal case when anormal or periodic RAU process fails, the RAU attempt counter is lessthan 5 and the GPRS update status is different from UPDATED (e.g. GU1).

If the TAU attempt counter is equal to 5, then the UE operates asfollows. The UE starts timer T3402 (i.e. timer which is started when theattempt counter is equal to 5 in the case of attach failure or TAUfailure and stopped when an attach request or a TAU requesat istransmitted), sets the EPS update status to NOT UPDATED (e.g. EU2),deletes the list of equivalent PLMNs and changes toEMM-REGISTERED.ATTEMPTING-TO-UPDATE state or optionally toEMM-REGISTERED.PLMN-SEARCH state in order to perform PLMN selection.

If A/Gb mode or Iu mode is supported by the UE, then the UE starts timerT3302 (i.e. timer which is started when the attempt counter is greaterthan 5 in the case of GPRS attach failure or RAU failure and stoppedwhen a GPRS attach request or a RAU requesat is transmitted), deletesthe list of equivalent PLMNs, sets the GPRS update state to NOT UPDATED(e.g. GU2) and changes to GMM-REGISTERED.ATTEMPTING-TO-UPDATE state oroptionally to GMM-REGISTERED.PLMN-SEARCH state in order to perform PLMNselection when a normal or periodic RAU procedure fails and the RAUattempt counter is greater than 5.

In the service request procedure, the following abnormal cases can beidentified in the UE.

a) When access is barred because of access class barring or NASsignaling connection establishment rejection by the network

If the service request procedure is started in response to a pagingrequest from the network, then access class barring is not applicable.

When the response to the paging request from the network triggers theservice request procedure and NAS signaling connection establishment isrejected by the network, the service request procedure is not started.The UE stays in the current serving cell and applies a normal cellreselection process. The service request procedure may be started if theservice request procedure is still necessary, i.e. when access for“terminating calls” is granted or because of cell change.

If the service request is initiated for CSFB, access is barred for “MO(mobile originated) CSFB” and the lower layer indicates “the barring isdue to CSFB specific access barring information”, then the servicerequest procedure is not started. The UE stays in the current servingcell and applies the normal cell reselection process. The servicerequest procedure may be started if the service request procedure isstill necessary, i.e. when access for “mobile originating CSFB” isgranted or because of cell change.

If the service request is initiated for CSFB, access is barred for “MOCSFB” and the lower layer does not indicate “the barring is due to CSFBspecific access barring information”, then the UE selects GERAN or UTRANradio access technology (RAT). The UE then proceeds with appropriate MMand CC (Call Control) specific procedures. The EMM sublayer does notindicate abortion of the service request procedure to the MM sublayer.

Otherwise, if access is barred for “originating calls”, then the servicerequest procedure is not started. The UE stays in the current servingcell and applies a normal cell reselection process. The service requestprocedure may be started if the service request procedure is stillnecessary, i.e. when access for “originating calls” is granted orbecause of cell change.

If the service request is initiated for 1×CSFB and access is barred for“originating calls”, then the UE selects cdma2000® 1×radio accesstechnology RAT). The UE then proceeds with appropriate cdma2000® 1×CSprocedures.

b) When NAS signaling connection is released or lower layer failureoccurs before the service request procedure is completed or before theservice reject message is received

If the service request is initiated for CSFB, then the UE selects GERANor UTRAN radio access technology (RAT). The UE then proceeds withappropriate MM and CC specific procedures. The EMM sublayer does notindicate abortion of the service request procedure to the MM sublayer.

If the service request is initiated for 1×CSFB, the UE may selectcdma2000® 1× RAT and proceed with appropriate cdma2000® 1×CS proceduresor perform cell selection.

Otherwise, the UE enters EMM-REGISTERED state. The UE aborts the servicerequest procedure, stops timer T3417 or T3417ext (i.e. timer which isstarted when an (extended) service request is transmitted) and stoppedwhen bearer is established or a service reject message is received) andreleases any resources allocated for the service request procedure.

c) When timer T3417 expires

The UE enters the EMM-REGISTERED state.

If the UE triggers the service request procedure from EMM-IDLE mode,then the EMM sublayer aborts the procedure and releases any resourcesallocated for the service request procedure.

If the UE triggers the service request procedure from EMM-CONNECTEDmode, then the EMM sublayer aborts the procedure and considers that the1×CSFB procedure has failed. The UE stays in EMM-CONNECTED mode.

d) When timer T3417ext expires

The UE enters the EMM-REGISTERED state.

If the UE triggers the service request procedure from EMM-IDLE mode,then the EMM sublayer aborts the procedure, indicates to the MM sublayerthat the CSFB procedure has failed and releases any resources allocatedfor the service request procedure.

If the UE triggers the service request procedure from EMM-CONNECTEDmode, then the EMM sublayer aborts the procedure and indicates to the MMsublayer that the CSFB procedure has failed. The UE stays in EMM-NNECTEDmode.

e) When the service reject message includes other EMM cause values than#3, #6, #7, #9, #10, #11, #35, #12, #13, #15, #18, #22, #25, #39 and #40and when the UE considers EMM cause #22 as an abnormal case

The UE aborts the procedure and enters EMM-REGISTERED state.

If the service request is initiated for CSFB, then the UE selects GERANor UTRAN as an RAT. The UE then proceeds with appropriate MM and CCspecific procedures. The EMM sublayer does not indicate abortion of theservice request procedure to the MM sublayer.

If the service request is initiated for 1×CSFB, then the UE selectscdma2000® 1×RAT. The UE then proceeds with appropriate cdma2000® 1×CSprocedures.

If the service request is initiated for 1×CSFB and the UE has dual Rx/Txconfiguration and supports enhanced 1×CSFB, then upon entering EMM-IDLEmode the UE performs the TAU procedure.

Here, EMM cause value #3 indicates an illegal UE, #6 indicates illegalmobile equipment (ME), #9 indicates that UE identification informationis not derived from the network, #10 indicates implicit detach, #11indicate non-granted PLMN, #35 indicates that a requested service optionis not authorized in the corresponding PLMN, #12 indicates a non-grantedtracking area, #13 indicates that roaming is not granted in thecorresponding tracking area, #15 indicates that an appropriate cell isnot present in a tracking area, #18 indicates that CS domain is notavailable, #22 indicates congestion, #25 indicates that a correspondingCSG (closed subscriber group) is not authorized, #39 indicates that CSservice is temporarily unavailable, and #40 indicates that activated EPSbearer context is not present. These values are exemplary EMM causevalues when the service request is not granted by the network.

The case in which the UE considers EMM cause value #22 as an abnormalcase corresponds to cases other than a case in which the TAU rejectmessage includes a predetermined timer (e.g. T3346 corresponding to anMM backoff timer set when NAS level MM congestion control is activated,MM signaling is normally barred during operation of T3346) and the timeris set to a non-zero value and is not deactivated.

f) When the TAU procedure is triggered

The UE aborts the service request procedure, stops timer T3417 orT3417ext if the timer is running and performs the TAU procedure. An“active” flag is set in the TAU request message. If the service requestis initiated for CSFB or 1×CSFB, then the UE sends the extended servicerequest message to the MME by using the existing NAS signalingconnection after the completion of the TAU procedure.

g) In the case of switch off

If the UE is in EMM-SERVICE-REQUEST-INITIATED state at switch off, thenthe detach procedure is performed.

h) When procedure collision occurs

When UE receives a detach request message with detach type “re-attachnot required” with EMM cause other than #2 indicating “IMSI unknown inHSS” or detach type “re-attach required” from the network inEMM-SERVICE-REQUEST-INITIATED state, then the detach procedureprogresses and the service request procedure is aborted.

Additionally, if the service request is initiated for CSFB or 1×CSFB,then the EMM sublayer indicates to the MM sublayer or cdma2000® upperlayers that the CSFB or 1×CSFB procedure has failed.

If the detach type information element in the detach request messageindicates “re-attach required”, then the attach procedure is performed.

When the UE receives a detach request message with detach type“re-attach not required” with EMM cause other than #2 indicating “IMSIunknown in HSS” or detach type “IMSI detach” from the network inEMM-SERVICE-REQUEST-INITIATED state, the UE progress both the servicerequest procedure and the detach procedure.

i) When a lower layer indicates service request message or extendedservice request message transmission failure with TAI change

If the current TAI is not in the TAI list, then the service requestprocedure is aborted to perform the TAU procedure. The “active” flag isset in the TAU request message. If the service request is initiated forCSFB or 1×CSFB, then the UE sends the extended service request messageto the MME by using the existing NAS signaling connection after thecompletion of the TAU procedure.

If the current TAI is still part of the TAI list, then the UE restartsthe service request procedure.

j) When a lower layer indicates service request message or extendedservice request message transmission failure without TAI change

The UE restarts the service request procedure.

k) When default or dedicated bearer setup fails

If the lower layers indicate radio bearer setup failure, then the UEdeactivates the EPS bearer.

l) When a lower layer indicates “extended wait time”

The UE aborts the service request procedure, enters EMM-REGISTEREDstate, and stops timer T3417 or T3417ext if the timer is still running.

The UE stops timer T3346 if it is running

The UE starts timer T3346 according to an “extended wait time” valueprovided by the lower layer.

The service request procedure is started if still necessary, when timerT3346 expires or is stopped.

If the service request is initiated for CSFB and timer T3246 (i.e. MMbackoff timer for CS domain) is not running, then the UE selects GERANor UTRAN as RAT. The UE then proceeds with appropriate MM and CCspecific procedures. The EMM sublayer does not indicate abortion of theservice request procedure to the MM sublayer.

If the service request is initiated for 1×CSFB, then the UE selectscdma2000® 1×RAT. The UE then proceeds with appropriate cdma2000® 1×CSprocedures or perform cell selection.

m) When timer T3346 is running

The UE does not start the service request procedure unless the UE hasPDN connection for emergency bearer services established or isestablishing PDN connection for emergency bearer services, or the UE isrequested by an upper layer for a CSFB for emergency call.

The UE stays in the current serving cell and applies normal cellreselection process. The service request procedure is started, if stillnecessary, when timer T3346 expires or is stopped.

Upon request of an upper layer for MO CSFB which is not for an emergencycall, if timer T3246 is not running, then the UE may select GERAN orUTRAN as RAT. The UE then proceeds with appropriate MM and CC specificprocedures. The EMM sublayer does not indicate abortion of the servicerequest procedure to the MM sublayer.

Upon request of the upper layer for CSFB for an emergency call, the UEselects GERAN or UTRAN as an RAT. The UE then proceeds with appropriateMM and CC specific procedures. The EMM sublayer does not indicateabortion of the service request procedure to the MM sublayer.

Upon request of the upper layer for 1×CSFB, the UE selects cdma2000®1×RAT. The UE then proceeds with appropriate cdma2000® 1×CS callprocedures.

Radio Link Failure (RLF)

RLF may occur between base stations (e.g. between an (e)NB or H(e)NB anda terminal (e.g. UE or MS). RLF refers to a state in which signaltransmission and reception are difficult to perform since quality of aradio link between a base station and a terminal is deteriorated.Operation related to RLF detection is performed in the RRC layer and aprocedure of discovering a new radio link is carried out upon detectionof RLF.

In 3GPP LTE, RRC (Radio Resource Control) state can be defined asRRC_CONNECTED state and RRC_IDLE state. The RRC_CONNECTED state refersto a state in which RRC connection is established between a base stationand a terminal and the terminal can transmit/receive data to/from thebase station in the RRC_CONNECTED state. The RRC_IDLE state refers to astate in which RRC connection between the base station and the terminalis released.

RLF related operations correspond to (1) detection of physical layerproblems in the RRC-CONNECTED state, (2) recovery of physical layerproblems and (3) RLF detection.

(1) Upon reception of consecutive “out-of-sync” indicationscorresponding to a predetermined value defined as N310 from a lowerlayer (e.g. PHY layer or MAC layer), a UE drives a timer defined asT310. The “out-of-sync” indications can be provided to a higher layer(e.g. layer higher than the RRC layer) when a PDCCH (Physical DownlinkControl Channel) received by a higher layer (physical layer) cannot bedemodulated or SINR (Signal-to-Interference plus Noise Ratio) is low.N310 and T310 can be provided as predetermined values as higher layerparameters.

(2) Upon reception of “in-sync” indications which are consecutive by apredetermined value defined as N311 from the lower layer duringoperation of the T310 timer, the UE stops the T310 timer. N311 can beprovided as a predetermined value as a higher layer parameter.

(3) The UE determines that RLF has been detected upon expiration of theT310 timer and initiates a connection re-establishment procedure.Expiration of the T310 timer means that the T310 timer reaches apredetermined time T310 without being stopped during operation. Theconnection re-establishment procedure refers to a procedure in which theUE sends an “RRC connection re-establishment request” message to thebase station, receives an “RRC connection re-establishment” message fromthe base station and transmits an “RRC connection re-establishmentcomplete” message to the base station. Refer to subclause 5.3.11 of 3GPPstandard document TS36.3331 for details of RLF related operations.

Enhanced NAS Signaling Request Procedure

When some or all NAS signaling requests (e.g. attach request, TAU/RAUrequest, service request, etc.) of a UE fail or are rejected by anetwork node (e.g. MME), as described above, the UE can operateaccording to cause values of NAS signaling request failure/rejection.For example, the UE can reattempt the NAS signaling requests. Here, theupper bound of reattempts can be set to 5 in the case of attach requestand TAU request. That is, the attach attempt counter or TAU attemptcounter can be incremented per failure and the maximum value can belimited to 5. In the case of service request, the upper bound of thenumber of attempts is not determined and the service request is definedin such a manner that the service request is reattempted after a standbytimer.

A NAS signaling request may fail or be rejected due to lower layerfailure (e.g. AS failure) or network failure (e.g. RLF detection,generation of abnormal network problems or problems of a core network)in 3GPP LTE/UMTS based mobile communication systems. Here, lower layerfailure related to NAS signaling request failure/rejection refers tofailure at the AS level. In case of network failure related to NASsignaling request failure/rejection, RLF can occur due to deterioratedstate of a radio access network between a UE/MS and an eNB/HeNB andabnormal network problems can be generated due to failure of NASsignaling connection between an eNB/HeNB and an MME/SGSN.

The present invention provides a method for improving inefficiency ofconventional procedures when a NAS signaling request fails or isrejected since lower layer failure and/or network failure occurs.

For example, when an uplink signal is weak while a downlink signal isstrong or when both the uplink signal and the downlink signal are weak,a NAS signaling request from a UE may not arrive at a base station (eNBor HeNB) and/or an MME. In this case, the NAS signaling requestinitiated by the UE may fail or may be rejected by the correspondingnetwork. In addition, when a network error is generated due to PLMNfailure or network failure, the NAS signaling request initiated by theUE may fail or may be rejected by the network.

According to the conventional procedures, when a NAS signaling requestfails or is rejected, the UE/MS reattempts the NAS signaling requestprocedure (in the case of attach request or TAU request, for example) orapplies a standby timer (in the case of the service request procedure)for the same RAT and/or the same PLMN. That is, the UE/MS reattempts theNAS signaling request or applies the standby timer while staying in thesame RAT and/or the same PLMN (i.e. without changing the RAT to anotherRAT or selecting another PLMN). In this case, if the correspondingnetwork failure cannot be recovered within a short time, services forusers may be considerably delayed.

Specifically, in an abnormal case in the UE in the NAS signaling requestprocedure as described above, a counter value increases and attachreattempt/TAU reattempt is performed when the attach attempt counter orTAU attempt counter is less than 5. In the case of service request,service request is reattempted after waiting for the standby timer (e.gT3417 or T3417ext).

In addition, even when a NAS signaling request is granted by thenetwork, part of the NAS signaling request may fail. For example,although the NAS signaling request procedure has been successfullyperformed for the EPS, MSC may not be reachable temporarily, networkfailure caused by PLMN failure may occur or the CS domain may not beavailable (for example, EMM cause value #16, #17 or #18 indicatingEPS-only success). In this case, the UE/MS performs NAS signalingrequest reattempt until the upper limit of the attempt counter accordingto the conventional procedures.

When the NAS signaling request is not granted by the network, causevalues #13, #14 and #35 of a reject message for the NAS signalingrequest correspond to a case in which the NAS signaling request isrejected due to roaming protocol and problems related to subscriberinformation although the cause values do not indicate networkfailure/lower layer failure. In this case, PLMN reselection and RATchange are immediately performed without reattempt counting according tothe conventional procedures. However, since the NAS signaling requestrejection is caused by subscriber information related problems ratherthan network failure/lower layer failure, the method for solvingproblems due to network failure/lower layer failure according to thepresent invention needs to be discriminated from the method for solvingservice delay problems due to service request procedure reattempt orwaiting.

According to the aforementioned conventional procedures, NAS signalingrequest reattempt is performed or the standby timer is applied when theNAS signaling request fails or is rejected due to network failure orlower layer failure. However, if network failure is so severe thatrecovery within a short time is not possible, it can be considered thatthere is no possibility that the NAS signaling request is granted by thenetwork even if the NAS signaling request procedure is reattempted orthe standby timer is applied. Accordingly, it is necessary to defineoperation of the UE/MS to immediately perform RAT change or PLMNreselection without NAS signaling request procedure reattempt or waitingwhen the NAS signaling request fails or is rejected due to networkfailure or lower layer failure. This can prevent the UE/MS fromperforming NAS signaling request reattempt whenever the NAS signalingrequest fails or is rejected due to network failure/lower layer failure,prevent unnecessary consumption of network resources by enabling theUE/MS to immediately perform RAT change/PLMN reselection and solveproblems of delaying service provided to users.

Embodiment 1

When a NAS signaling request (e.g. attach, TAU/RAU, service request,etc.) fails or is rejected by the network due to lower layer failure ornetwork failure, the UE/MS can immediately perform RAT change or PLMNreselection, or simultaneously carry out RAT change and PLMNreselection. Here, the network failure includes CS failure, PS failureor both CS failure and PS failure. The network failure may be caused byat least one of RLF, network abnormal cases or core network problems. Anembodiment of the present invention will now be described.

1) In the case of attach request or TAU/RAU request, the UE/MS performsPLMN reselection and/or RAT change after attempting the upper bound(e.g. 5) of the attempt counter.

2) While the upper bound of the attempt counter is not applied in theconventional service request procedure, the upper bound is applied tothe service request procedure in the present invention. For example, anattempt counter having a predetermined upper bound can be applied or aperiod in which the service request procedure is performed can be set,similarly to the attach procedure of TAU/RAU procedure. Accordingly, theUE/MS can perform PLMN reselection and/or RAT change after carrying outthe service request procedure until the upper bound of the attemptcounter is reached.

3) Even when the value of the attempt counter of the UE/MS is less thanthe upper bound, the UE/MS updates (or sets) the attempt counter valueto the upper bound without performing reattempt. That is, the UE/MS canperform operation (i.e. RAT change and/or PLMN reselection)corresponding to the upper bound of the attempt counter without theupper bound attempts.

1), 2) and 3) may be independently applied or one or more thereof may besimultaneously applied.

For example, when NAS signaling request filature or rejection occurs dueto network failure, the UE/MS can perform RAT change and/or PLMNselection without carrying out attempts or waiting (i.e. without settingthe attempt counter to the upper bound (e.g. 5) for the attach procedureor TAU/RAU procedure and without applying the standby timer for theservice request procedure) in the attach procedure, TAU/RAU procedure orservice request procedure.

Furthermore, the aforementioned operation when the attempt counter valueis set to the upper bound in an abnormal case of the UE/MS can beadditionally performed as an operation when the attempt counter value isset to the upper bound in the present invention. That is, the UE can setthe EPS update status to NOT UPDATED (e.g. EU2), delete a GUTI, lastvisited registered TAI, eKSI and a list of equivalent PLMNs if present,and then change to EMM-DEREGISTERED.PLMN-SEARCH state to perform PLMNselection. In addition, when the UE supports A/Gb mode or Ui mode, theUE can set the GPRS update status to NOT UPDATED (e.g. GU2) and deleteRAI, P-TMSI, P-TSMI signature and a GPRS ciphering key sequence numberif present.

Embodiment 2

As described in embodiment 1, the UE/MS can perform RAT change and/orPLMN selection when NAS signaling request failure or rejection occursdue to lower layer failure or network failure. In this case, it can beassumed that a different RAT is selected in the same PLMN as that of acell in which network failure has occurred or a PLMN equivalent to thePLMN of the cell is selected. In addition, the UE/MS, which has selectedthe different RAT, may return to the cell in which network failure hasoccurred according to AS reselection (e.g. RAT change). Here, if thenetwork failure is severe and thus cannot be solved within a short time,the network failure is not overcome even if the UE/MS returns to theprevious RAT/PLMN and thus the NAS signaling request of the UE/MS mayfails/be rejected again. In this case, while the UE/MS can immediatelyperform RAT change/PLMN selection and be served by another RAT/PLMN, asdescribed in embodiment 1, the procedure in which the UE/MS returns toRAT/PLMN having problems may be repeated. This problem may be referredto as a Ping-Pong problem due to network failure. The present embodimentproposes a method for solving the Ping-Pong problem.

1) In the case of NAS signaling request failure or rejection due tolower layer failure or network failure, the UE/MS can start apredetermined timer (i.e. RAT/PLMN selection related timer) whenselecting a different RAT in the same PLMN or selecting a different RATin an equivalent (or different) PLMN. That is, the RAT/PLMN selectionrelated timer can be defined as a timer related to selection of an RATand/or a PLMN other than the current RAT and PLMN in which networkfailure occurs (i.e. selection of an RAT other than the current RAT of aPLMN other than the current PLMN, the same RAT of the other PLMN or theother RAT of the same PLMN). That is, the RAT/PLMN selection relatedtimer can be understood as a timer for preventing the UE/MS fromselecting the current RAT+PLMN in which network failure occurs duringoperation of the timer. Since the possibility of network failurerecovery needs to be considered even though network failure is so severethus recovery within a short time is not possible, the value of theRAT/PLMN selection related timer can be appropriately set. That is, thetimer can be set to a value at which network failure recovery isexpected. In addition, the UE can disable LTE capability duringoperation of the RAT/PLMN selection related timer and re-enable LTEcapability upon expiration of the RAT/PLMN selection related timer.

2) While the UE can select another RAT and/or another PLMN and disableLTE capability when the NAS signaling request fails or is rejected dueto lower layer failure or network failure, as described in 1), the UEmay select the previous RAT and the previous PLMN and re-enable LTEcapability when predetermined conditions are satisfied. Thepredetermined conditions may include power off/on of the UE, networkoperation mode change, etc. for PLMN selection.

3) If NAS does not select a non-equivalent PLMN, a lower layer (i.e. AS)can consider the LTE cell status as barred for a period of time (e.g.,similar procedure for a not-allowed CSG cell). The AS can reselectanother RAT or cell based on a ranking algorithm thereof instead of NASdisabling all LTE cells.

1), 2) and 3) may be independently applied and one or more thereof maybe simultaneously applied.

For example, when a NAS signaling request fails or is rejected due tonetwork failure, the UE/MS can set the attempt counter to the upperbound (e.g. 5) thereof and start the RAT/PLMN selection related timer inattach request, TAU/RAU and service request procedures. During operationof the RAT/PLMN selection related timer, the UE/MS can select an RATand/or a PLMN from RATs and/or PLMNs other than the RAT and/or PLMN(i.e. current RAT and PLMN) in which NAS signaling requestfailure/rejection occurs.

FIG. 6 is a flowchart illustrating a method for performing a NASsignaling procedure according to an embodiment of the present invention.

A UE may transmit a request message (e.g. attach request, TAU request,RAU request or service request message) to a network node (e.g. MME) ofa first network in step S610.

The UE may receive a message (e.g. attach reject, TAU reject, RAU rejector service reject message) including information indicating networkfailure in the first network from the network node of the first networkin step S620. While FIG. 6 shows reception of a reject message whichindicates network failure, the UE may receive a NAS signaling requestfailure message which indicates lower layer failure in step S620.

The UE may start a network selection related timer in step S630 andselect a second network during operation of the timer in step S640.Here, the network selection related timer may correspond to the RAT/PLMNselection related timer described in embodiment 2. That is, the UE canselect a new RAT and/or a new PLMN from network candidates other than acombination of the current RAT and PLMN in which network failure occurs.

The above-described embodiments of the present invention can beindependently applied or two or more embodiments can be simultaneouslyapplied.

FIG. 7 illustrates a configuration of a UE according to an embodiment ofthe present invention.

Referring to FIG. 7, a UE 1000 according to the present invention mayinclude a transmission and reception module 1010, a processor 1020 and amemory 1030. The transmission and reception module 1010 may beconfigured to transmit signals, data and information to an externaldevice (e.g. network node, another UE, server, eNB or the like) and toreceive signals, data and information from an external device (e.g.network node, another UE, server, eNB or the like). The processor 1020may be configured to control overall operations of the UE 1000 and toprocess information which is transmitted/received by the terminal 1000to/from the external device. The memory 1030 may store processedinformation for a predetermined time and be replaced by a component suchas a buffer (not shown).

The UE according to an embodiment of the present invention may beconfigured to perform a NAS signaling procedure. The processor 1020 maybe configured to receive a first message including information whichindicates network failure from the network node of the first networkusing the transmission and reception module 1010. In addition, theprocessor 1020 may start a network selection related timer and select asecond network from network candidates other than the first networkwhile the network selection related timer is running.

The configuration of the UE 1000 may be implemented such that theabove-described embodiments of the present invention are independentlyapplied or two or more embodiments are simultaneously applied anddescription of redundant parts is omitted for clarity.

The embodiments of the present invention may be achieved by variousmeans, for example, hardware, firmware, software, or a combinationthereof.

In a hardware configuration, the methods according to the embodiments ofthe present invention may be achieved by one or more ApplicationSpecific Integrated Circuits (ASICs), Digital Signal Processors (DSPs),Digital Signal Processing Devices (DSPDs), Programmable Logic Devices(PLDs), Field Programmable Gate Arrays (FPGAs), processors, controllers,microcontrollers, microprocessors, etc.

In a firmware or software configuration, the embodiments of the presentinvention may be implemented in the form of a module, a procedure, afunction, etc. For example, software code may be stored in a memory unitand executed by a processor. The memory unit is located at the interioror exterior of the processor and may transmit data to and receive datafrom the processor via various known means.

The detailed description of the preferred embodiments of the presentinvention is given to enable those skilled in the art to realize andimplement the present invention. While the present invention has beendescribed with reference to the preferred embodiments of the presentinvention, those skilled in the art will appreciate that manymodifications and changes can be made to the present invention withoutdeparting from the spirit and essential characteristics of the presentinvention. For example, the structures of the above-describedembodiments of the present invention can be used in combination. Theabove embodiments are therefore to be construed in all aspects asillustrative and not restrictive. Therefore, the present invention isnot intended to limit the embodiments disclosed herein but to give abroadest range matching the principles and new features disclosedherein.

INDUSTRIAL APPLICABILITY

The above-described embodiments of the present invention are applicableto various mobile communication systems.

The invention claimed is:
 1. A method for performing a non-accessstratum (NAS) signaling procedure by a UE (User Equipment) in a wirelesscommunication system, the method comprising, transmitting, by the UE, anattach request message to a first network of a first radio accesstechnology (RAT) in a first public land mobile network (PLMN), whereinthe first RAT of the first network is Long Term Evolution (LTE);receiving, by the UE, an attach reject message informing networkfailure, in response to the attach request message, starting, by the UE,a network selection related timer after receiving the attach rejectmessage; and selecting, by the UE, a second network from among networkcandidates, while the network selection related timer is running,wherein the network candidates include a second RAT in the first PLMN, afirst RAT in a second PLMN and a second RAT in the second PLMN, andwherein at least one of the network candidates includes an LTE RAT. 2.The method according to claim 1, wherein the attach reject message is arejection message informing that the NAS signaling procedure requestedthrough the attach request message is not granted by a network.
 3. Themethod according to claim 1, wherein a RAT of the first network is LTE(Long Term Evolution).
 4. A user equipment (UE) configured to perform anon-access stratum (NAS) signaling procedure in a wireless communicationsystem, comprising: a transmitting device and a reception device; and aprocessor configured to: transmit an attach request message to a firstnetwork of a first radio access technology (RAT) in a first public landmobile network (PLMN) via the transmitting device, wherein the first RATof the first network is Long Term Evolution (LTE); receive an attachreject message informing network failure, in response to the attachrequest message via the reception device, start a network selectionrelated timer after receiving the attach reject message; and select asecond network from among network candidates, while the networkselection related timer is running, wherein the network candidatesinclude a second RAT in the first PLMN a first RAT in a second PLMN anda second RAT in the second PLMN, and wherein at least one of the networkcandidates includes an LTE RAT.
 5. The user equipment according to claim4, wherein the attach reject message is a rejection message informingthat the NAS signaling procedure requested through the attach requestmessage is not granted by a network.
 6. The user equipment according toclaim 4, wherein a RAT of the first network is LTE (Long TermEvolution).